home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
testreq.zip
/
TESTREQ.DOC
next >
Wrap
Text File
|
1992-03-13
|
7KB
|
155 lines
testreq v0.4
Testreq has been modified once again in the area of FD system filenames.
Testreq will first look for SETUP.FD and if not found it will then look
for the older FD.SYS config file.
Please note that if Testreq finds SETUP.FD it will then expect
request.FD and if FD.SYS is used, request.SYS is expected.
You may merely copy request.fd to request.sys if need be.
------------------------------------------------------------------------
testreq v0.3
Testreq has been updated to work with FrontDoor 2.01. The ONLY change
has been to accomodate the change in FD filenames from FD.SYS =>
FDSETUP.FD and REQUEST.SYS => REQUEST.FD.
Any quirks, mites, bugs, etc., which may have existed in v0.2
still exist in v0.3.
-----------------------------------------------------------------------
testreq v0.2
after a recent bout of BrainDamage<tm> and some embarrasing moments
by royally screwing up a magic filename setup for my beta testers, I
decided to write this little program. It's very green and was written
in a few hours, so don't expect too much. I haven't tried REAL hard to
make it break, so you may find that it will. If so, I'd like to hear
about it.
First the warnings: ummm... none that I can think of. TestReq doesn't
WRITE to anything but your screen (and it doesn't even do that
'directly') so it shouldn't be able to really hurt anything. Still, I
guarantee nothing. TestReq may or may not be accurate depending on how
it is used and it may or may not work at all!
How it is _supposed_ to work is this... run Testreq and supply either a
filename (wildcards are ok) or a magic name that you _think_ should
result in a file being sent when such a request comes in. Don't use a
path since an incoming request wouldn't have a path on it.
If in fact the file is locatable by FD, TestReq should be able to find
it too... at least that's the plan :-) TestReq will then display ALL
matches that FD would find for that particular request. If you were to
type...
TestReq *.zip
it should list all eight zillion files in your requestable directories.
If the file would not be sent by FD, TestReq won't find it either, with
one exception, password protected directories or filenames.
TestReq does not skip the file or directory if it is password protected.
Instead, TestReq will display the path\filename and next to it display
the password in the form '!password'. That way, you'll know that when
someone requests the filename you provided to TestReq, they're gonna
need to supply the displayed password too. The '!' character is
prepended to the password just to make it stand out a bit and of course
is not part of the password.
TestReq will first look for the environmental variable 'FD'. If found,
it'll follow this path to find FD.SYS. If not found it will look in the
current directory for FD.SYS. If FD.SYS ain't there, Testreq ends.
When FD.SYS is found, Testreq then looks for REQUEST.SYS in what FD.SYS
says is the system directory. It's ok if REQUEST.SYS is zero bytes long
(as it might be if you had password protected files at one time then
deleted all files & passwords) or non-existant. If it's zero bytes or
not there it just won't be checked for passwords.
FD.SYS also provides the path\filename of your ALIAS list and your
requestable directories list.
These items are found in SETUP => Mailer => File Requests. The second
item in the 'File Requests' screen is labeled 'List'. This is what I
will (from now on) call your OKFILES list. The third item on this
screen is labeled ALIAS and is your list of ALIAS or MAGIC filenames.
*** NOTE *** CAUTION *** WARNING *** LOOKYHERE ***
TestReq does NOT assume anything with the OKFILES and ALIAS list. If
you have defined these filenames without a path, TestReq assumes they
are in the current directory.
FD seems to work the same way. I run FD from my RemoteAccess directory.
If I don't define the full path to my OKFILES and ALIAS list, FD
generates an error trying to open those files when a request comes in.
It seems that there are quite a few possibilites when it comes to how
files are password protected. At this point in time I'm still not sure
what, as SETUP calls it, a 'Unique portion thereof' is for the
Filename\Path field in the Setup => Manager => Requests screen.
Since I don't have a second mailer and computer with which to make
multiple tests, I have to wait for some feedback on what others are
using successfully and how TestReq reacts to 'odd' setups.
In FD's SETUP Filename\path field, TestReq expects to find:
1) a full path. i.e. Drive:path WITH a trailing backslash. This is how
_I_ would password protect an entire directory, and that seems to
work.
2) Anything that doesn't have a trailing backslash is considered to be
a filename or a magic name.
In other words, if you have an entry like this in the request manager...
Filename or path Password
----------------------------------------------------------------------
C:\Files\Newfiles YourPassword
TestReq will consider "NewFiles" to be a filename or Magic name rather
than a subdirectory.
And of course TestReq could care less about time of day you may have
defined as "no requests", events that don't allow requests and/or what
types of systems (listed, unlisted, etc.) may request. That wouldn't
make much sense since you might run TestReq during an event that doesn't
allow requests, and yet a request may come in under another event, or a
request might come in... well, the possibilities just boggle the mind!
The best way to get the feel of how TestReq works is to just go ahead
and use it. Try 'TestReq Files' and see if it reports the correct file
that is sent when someone requests FILES. Try it with a file you know
to be password protected or try a magic name you have set up.
One item that is known NOT to work is a magicname with multiple files.
In otherwords, if you defined a magicname like this:
RA c:\files\ra_00?.zip c:\files\ra_upd.zip
FrontDoor would send BOTH files when receiving "RA" as a magic name
request. TestReq presently only reports the first filename. This is
due to be fixed in a future version.
Any feedback is appreciated and bug fixes, enhancements will be taken
into consideration.
enjoy,
Mike Janke, 1:135/4
Data (305)271-2146